Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d5062ea8a3d01f00c2418cb390830b6afbb14aa7e6e1d27212e2a8be2c07e152

Tx prefix hash: 1039db3df945ea4d56045849c017433239f8bbdb0ff249e20b8ea8adb6f7206d
Tx public key: 689d300df2cdd818b737cd741853d6e553ab71796dc847515ca3c2c91872803c
Timestamp: 1703157437 Timestamp [UCT]: 2023-12-21 11:17:17 Age [y:d:h:m:s]: 01:105:17:39:26
Block: 917921 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 336686 RingCT/type: yes/0
Extra: 01689d300df2cdd818b737cd741853d6e553ab71796dc847515ca3c2c91872803c02110000000e0011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d5745dc687a437dadbf7db5ad5571cbaab1cc8c5c0a51da06904194b1fbe764c 0.600000000000 1375545 of 15

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": 917931, "vin": [ { "gen": { "height": 917921 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d5745dc687a437dadbf7db5ad5571cbaab1cc8c5c0a51da06904194b1fbe764c" } } ], "extra": [ 1, 104, 157, 48, 13, 242, 205, 216, 24, 183, 55, 205, 116, 24, 83, 214, 229, 83, 171, 113, 121, 109, 200, 71, 81, 92, 163, 194, 201, 24, 114, 128, 60, 2, 17, 0, 0, 0, 14, 0, 17, 5, 91, 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