Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 49bbc36a21b1a5017bd89b56411572e8fe68180f0c65bf14cb967e815fbfe8f0

Tx prefix hash: fd35e9a75a0f68f0866d399a3aa96d84414a93c84a47add4619c7f5c5bf58570
Tx public key: fbce8e8dc90f1853aab83296f81debbc3bd39226079b488947cbbb066acb86d4
Timestamp: 1672545217 Timestamp [UCT]: 2023-01-01 03:53:37 Age [y:d:h:m:s]: 02:031:04:25:43
Block: 664991 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 543946 RingCT/type: yes/0
Extra: 01fbce8e8dc90f1853aab83296f81debbc3bd39226079b488947cbbb066acb86d402110000000452542ceb000000000000000000

1 output(s) for total of 3.842454475000 dcy

stealth address amount amount idx
00: e0174f6ed8c0a0f4b3dc77f241b374de864c73d27b4d08a4e57f3117679bcbe8 3.842454475000 1106006 of 0

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": 665001, "vin": [ { "gen": { "height": 664991 } } ], "vout": [ { "amount": 3842454475, "target": { "key": "e0174f6ed8c0a0f4b3dc77f241b374de864c73d27b4d08a4e57f3117679bcbe8" } } ], "extra": [ 1, 251, 206, 142, 141, 201, 15, 24, 83, 170, 184, 50, 150, 248, 29, 235, 188, 59, 211, 146, 38, 7, 155, 72, 137, 71, 203, 187, 6, 106, 203, 134, 212, 2, 17, 0, 0, 0, 4, 82, 84, 44, 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