Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6cbd67b1878847f67e2dd0f87f0c41a5b27b6e33799fbb942bb6b443540bcbb3

Tx prefix hash: 5c0ac6de67fc3008676daee129b4349f00ab224aa5d83fe58f52d9975655ae8f
Tx public key: 548e4d328c0fe7affa038bd580d4b6e7144535d4fcc46d065469774010c4fee1
Timestamp: 1716334290 Timestamp [UCT]: 2024-05-21 23:31:30 Age [y:d:h:m:s]: 00:246:02:58:27
Block: 1027165 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 176099 RingCT/type: yes/0
Extra: 01548e4d328c0fe7affa038bd580d4b6e7144535d4fcc46d065469774010c4fee102110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 400cf7485cc4c68d972ca3be1b00a388054d59f7446927277c0e2f7cf82484ac 0.600000000000 1494648 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": 1027175, "vin": [ { "gen": { "height": 1027165 } } ], "vout": [ { "amount": 600000000, "target": { "key": "400cf7485cc4c68d972ca3be1b00a388054d59f7446927277c0e2f7cf82484ac" } } ], "extra": [ 1, 84, 142, 77, 50, 140, 15, 231, 175, 250, 3, 139, 213, 128, 212, 182, 231, 20, 69, 53, 212, 252, 196, 109, 6, 84, 105, 119, 64, 16, 196, 254, 225, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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