Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: ede053940ec518d11eb9c2eee4f2018ae0e9a83a6bc4dfc387df6c73493923ed

Tx prefix hash: d31cd1416f13311bde4b3641e7518d17442f5e9e747c395ccce98c31e4bde9be
Tx public key: 2a079d26a95e09870b3f1d734d6c8449844a782675f4f18b58b43bf3ea5f692d
Timestamp: 1696895845 Timestamp [UCT]: 2023-10-09 23:57:25 Age [y:d:h:m:s]: 01:037:10:25:32
Block: 866225 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 287958 RingCT/type: yes/0
Extra: 012a079d26a95e09870b3f1d734d6c8449844a782675f4f18b58b43bf3ea5f692d021100000003e6d27f9c000000000000000000

1 output(s) for total of 0.827631517000 dcy

stealth address amount amount idx
00: 740e098033018770c891f57d3ef72907bee83fb22c5d3dca8edd50f5ba0a6b85 0.827631517000 1320803 of 0

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 866235, "vin": [ { "gen": { "height": 866225 } } ], "vout": [ { "amount": 827631517, "target": { "key": "740e098033018770c891f57d3ef72907bee83fb22c5d3dca8edd50f5ba0a6b85" } } ], "extra": [ 1, 42, 7, 157, 38, 169, 94, 9, 135, 11, 63, 29, 115, 77, 108, 132, 73, 132, 74, 120, 38, 117, 244, 241, 139, 88, 180, 59, 243, 234, 95, 105, 45, 2, 17, 0, 0, 0, 3, 230, 210, 127, 156, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8