Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a677ba463e82c5c6cf842401ff160a2c7b2f222d1cbecc0b0f14f2691b760281

Tx prefix hash: b1b25b684dae0c5eaa0bda58756bece07629069d7c7568cb48405e6d5eb9cfdb
Tx public key: ec804e19b271875948acdf6535b06828329b086c3f4022ab1c84d0c7b4a4ec68
Timestamp: 1704102256 Timestamp [UCT]: 2024-01-01 09:44:16 Age [y:d:h:m:s]: 01:136:17:03:40
Block: 925751 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 358850 RingCT/type: yes/0
Extra: 01ec804e19b271875948acdf6535b06828329b086c3f4022ab1c84d0c7b4a4ec680211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 892243f82d74288bf461024c6d0f48acba47f9e352aebddfa7299c544c145a6c 0.600000000000 1383517 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": 925761, "vin": [ { "gen": { "height": 925751 } } ], "vout": [ { "amount": 600000000, "target": { "key": "892243f82d74288bf461024c6d0f48acba47f9e352aebddfa7299c544c145a6c" } } ], "extra": [ 1, 236, 128, 78, 25, 178, 113, 135, 89, 72, 172, 223, 101, 53, 176, 104, 40, 50, 155, 8, 108, 63, 64, 34, 171, 28, 132, 208, 199, 180, 164, 236, 104, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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