Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 315430beb051cfec4ebb9942d6f05cc37a8f35727392172d0678f036f4670102

Tx prefix hash: 261c29d8ccd0949103244125eb8277df0dd7b831af540f24b465d45c3e2bceb4
Tx public key: 61ae2ce8422be92061ec8e28267e6b3351fd43ab4755f0b2ebd11320f4e71cd7
Timestamp: 1574492970 Timestamp [UCT]: 2019-11-23 07:09:30 Age [y:d:h:m:s]: 05:003:20:34:56
Block: 15190 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0986 kB
Tx version: 2 No of confirmations: 1145947 RingCT/type: yes/0
Extra: 0161ae2ce8422be92061ec8e28267e6b3351fd43ab4755f0b2ebd11320f4e71cd7021100000013f95225a5000000000000000000

1 output(s) for total of 546.600605197000 dcy

stealth address amount amount idx
00: 976c92420d1480a2aadd47140ac80e42f5cb06bec4e405455d17bc15a33e4be8 546.600605197000 20142 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": 15200, "vin": [ { "gen": { "height": 15190 } } ], "vout": [ { "amount": 546600605197, "target": { "key": "976c92420d1480a2aadd47140ac80e42f5cb06bec4e405455d17bc15a33e4be8" } } ], "extra": [ 1, 97, 174, 44, 232, 66, 43, 233, 32, 97, 236, 142, 40, 38, 126, 107, 51, 81, 253, 67, 171, 71, 85, 240, 178, 235, 209, 19, 32, 244, 231, 28, 215, 2, 17, 0, 0, 0, 19, 249, 82, 37, 165, 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