Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d04b5367f1a96907d27277bb89bb5849680bf45f5fe5cf98952a6b81d8f0b3d4

Tx prefix hash: a68b7bfa260d731ee80125314e794c8e9ca4fed9c8e23a3b81b98e2aa6b57d99
Tx public key: 56d8daf9f861bbbc48c41a93242db1263860cb095e13dc7a1bd9e59f4d304080
Timestamp: 1673961924 Timestamp [UCT]: 2023-01-17 13:25:24 Age [y:d:h:m:s]: 02:081:12:20:59
Block: 676737 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 579911 RingCT/type: yes/0
Extra: 0156d8daf9f861bbbc48c41a93242db1263860cb095e13dc7a1bd9e59f4d3040800211000000025ec35160000000000000000000

1 output(s) for total of 3.513090514000 dcy

stealth address amount amount idx
00: 4fc9cb16da958420d466426c380ed273007bc090ed186beb38cbdec40695c441 3.513090514000 1118464 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": 676747, "vin": [ { "gen": { "height": 676737 } } ], "vout": [ { "amount": 3513090514, "target": { "key": "4fc9cb16da958420d466426c380ed273007bc090ed186beb38cbdec40695c441" } } ], "extra": [ 1, 86, 216, 218, 249, 248, 97, 187, 188, 72, 196, 26, 147, 36, 45, 177, 38, 56, 96, 203, 9, 94, 19, 220, 122, 27, 217, 229, 159, 77, 48, 64, 128, 2, 17, 0, 0, 0, 2, 94, 195, 81, 96, 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