Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8929d890856232c0e541f81f7c90ab20d81e3140fb2fe2e64025ffe4f630531a

Tx prefix hash: 9775b864749c200424a76cac4130de097d3e9cd5fd8110ce6a28c22ba34aee20
Tx public key: 454e5d3d8ab3a0fe9705ddde3928f2e0182174a28614aa9db14f67af5f1a0ce1
Timestamp: 1702688055 Timestamp [UCT]: 2023-12-16 00:54:15 Age [y:d:h:m:s]: 01:036:07:27:18
Block: 914028 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 287261 RingCT/type: yes/0
Extra: 01454e5d3d8ab3a0fe9705ddde3928f2e0182174a28614aa9db14f67af5f1a0ce102110000000175e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2c543bf6a52129d31a7f92e16106459474a7fb2bf3363ab2bc9425af516af8da 0.600000000000 1371310 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": 914038, "vin": [ { "gen": { "height": 914028 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2c543bf6a52129d31a7f92e16106459474a7fb2bf3363ab2bc9425af516af8da" } } ], "extra": [ 1, 69, 78, 93, 61, 138, 179, 160, 254, 151, 5, 221, 222, 57, 40, 242, 224, 24, 33, 116, 162, 134, 20, 170, 157, 177, 79, 103, 175, 95, 26, 12, 225, 2, 17, 0, 0, 0, 1, 117, 227, 240, 233, 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