Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c854c44488ba22a38ff9071ca75460872f958b4ef8c90dac363b13c3f44f4a30

Tx prefix hash: 5d3cec0ba6fb9ad47895374550d5389d22b2b8ca9a74bfe761b79504bcdda505
Tx public key: d00ad697260a081e14b3c67be1a1f3fcfc3a898296cf1620d6f6c7f44ae3c4f8
Timestamp: 1583235838 Timestamp [UCT]: 2020-03-03 11:43:58 Age [y:d:h:m:s]: 05:053:14:23:36
Block: 75374 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1193464 RingCT/type: yes/0
Extra: 01d00ad697260a081e14b3c67be1a1f3fcfc3a898296cf1620d6f6c7f44ae3c4f802110000004603d36d11000000000000000000

1 output(s) for total of 345.346807412000 dcy

stealth address amount amount idx
00: 1ae59968c947fc033d7adf2d1cc994df9e5d12667dab42c05676c41aae63c182 345.346807412000 139311 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": 75384, "vin": [ { "gen": { "height": 75374 } } ], "vout": [ { "amount": 345346807412, "target": { "key": "1ae59968c947fc033d7adf2d1cc994df9e5d12667dab42c05676c41aae63c182" } } ], "extra": [ 1, 208, 10, 214, 151, 38, 10, 8, 30, 20, 179, 198, 123, 225, 161, 243, 252, 252, 58, 137, 130, 150, 207, 22, 32, 214, 246, 199, 244, 74, 227, 196, 248, 2, 17, 0, 0, 0, 70, 3, 211, 109, 17, 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