Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 71ce67801ef555e74455bf5f94dc8bc6626957788788dad83c9e166b2d5a9164

Tx prefix hash: 3ce80cd8b194caa1e42ad8be086e70ba0c921a6d349894b2106a83a55ada6e5f
Tx public key: ed184fd7476d78684ce0fc88c832318396b272c1a34bff9fad6e54ccdf7510a8
Timestamp: 1729155817 Timestamp [UCT]: 2024-10-17 09:03:37 Age [y:d:h:m:s]: 00:148:06:32:13
Block: 1133464 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 105750 RingCT/type: yes/0
Extra: 01ed184fd7476d78684ce0fc88c832318396b272c1a34bff9fad6e54ccdf7510a802110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ddc675226c6c8451a47a65e42b76de6e7381620974aef6be61ea4b8b4b100c50 0.600000000000 1616585 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": 1133474, "vin": [ { "gen": { "height": 1133464 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ddc675226c6c8451a47a65e42b76de6e7381620974aef6be61ea4b8b4b100c50" } } ], "extra": [ 1, 237, 24, 79, 215, 71, 109, 120, 104, 76, 224, 252, 136, 200, 50, 49, 131, 150, 178, 114, 193, 163, 75, 255, 159, 173, 110, 84, 204, 223, 117, 16, 168, 2, 17, 0, 0, 0, 2, 145, 225, 60, 4, 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