Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 277f5d5864bb4fb579f05b70a4d6bdbb2b55702cfbd262598a51628c36b41c45

Tx prefix hash: 2f64a97c16cada3e52e333c49690094bc326fe4dcab07c2a879548c8354306d0
Tx public key: 6806f815e5070e6a0b3f0c4a3597d4d3ce6334d214f7f4abde8a1c7321d99050
Timestamp: 1736210704 Timestamp [UCT]: 2025-01-07 00:45:04 Age [y:d:h:m:s]: 00:110:07:44:57
Block: 1191807 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 78652 RingCT/type: yes/0
Extra: 016806f815e5070e6a0b3f0c4a3597d4d3ce6334d214f7f4abde8a1c7321d99050021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fa3f35f1d698563f138745165382febdc97774907d297744bf91858e6a7a3a63 0.600000000000 1678350 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": 1191817, "vin": [ { "gen": { "height": 1191807 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fa3f35f1d698563f138745165382febdc97774907d297744bf91858e6a7a3a63" } } ], "extra": [ 1, 104, 6, 248, 21, 229, 7, 14, 106, 11, 63, 12, 74, 53, 151, 212, 211, 206, 99, 52, 210, 20, 247, 244, 171, 222, 138, 28, 115, 33, 217, 144, 80, 2, 17, 0, 0, 0, 4, 0, 127, 151, 138, 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