Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 50ab5d17033b6295a5c66923054099d2dd263e6f4ef489b9f76f8843c6a94bd4

Tx prefix hash: 214f3772e1009190f246188743296b8f4fa1df4dc6377c0a9f562381c9e768a2
Tx public key: 25a5f88b92865576855c5f44f93cc78afe7f37b7720f3e2bceec8a8099573840
Timestamp: 1577787250 Timestamp [UCT]: 2019-12-31 10:14:10 Age [y:d:h:m:s]: 04:274:18:04:30
Block: 35626 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1085519 RingCT/type: yes/0
Extra: 0125a5f88b92865576855c5f44f93cc78afe7f37b7720f3e2bceec8a8099573840021100000085feadaf7f000000000000000000

1 output(s) for total of 467.688969332000 dcy

stealth address amount amount idx
00: 8d78e459968e24ab944ebe31b562c5b02ffd6826b955b61a188212953cdf3730 467.688969332000 60133 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": 35636, "vin": [ { "gen": { "height": 35626 } } ], "vout": [ { "amount": 467688969332, "target": { "key": "8d78e459968e24ab944ebe31b562c5b02ffd6826b955b61a188212953cdf3730" } } ], "extra": [ 1, 37, 165, 248, 139, 146, 134, 85, 118, 133, 92, 95, 68, 249, 60, 199, 138, 254, 127, 55, 183, 114, 15, 62, 43, 206, 236, 138, 128, 153, 87, 56, 64, 2, 17, 0, 0, 0, 133, 254, 173, 175, 127, 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