Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8dc830c8ef4640bc3975e611d6d44fd7cb25fefbe181ebe3c01f822973000b9e

Tx prefix hash: 98dd4a3f722b7dfb5a02d52b2b3f929fe0aa4dfa1170b49a6c754b0351eea169
Tx public key: 521e7bed076833c4ef0f9c3a257bdd29c4c3effc8ce521fc4a0fef99213ff9c4
Timestamp: 1732128002 Timestamp [UCT]: 2024-11-20 18:40:02 Age [y:d:h:m:s]: 00:003:07:14:08
Block: 1158003 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 2374 RingCT/type: yes/0
Extra: 01521e7bed076833c4ef0f9c3a257bdd29c4c3effc8ce521fc4a0fef99213ff9c40211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c04319c6c52345e65651468aa0afab357f18b34b4a68186e1c1e0e4a85bdf438 0.600000000000 1643628 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": 1158013, "vin": [ { "gen": { "height": 1158003 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c04319c6c52345e65651468aa0afab357f18b34b4a68186e1c1e0e4a85bdf438" } } ], "extra": [ 1, 82, 30, 123, 237, 7, 104, 51, 196, 239, 15, 156, 58, 37, 123, 221, 41, 196, 195, 239, 252, 140, 229, 33, 252, 74, 15, 239, 153, 33, 63, 249, 196, 2, 17, 0, 0, 0, 4, 31, 10, 83, 235, 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