Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0f41fa48986315aba0028c1f7eaaf342ad709849bfbb3d57cf5db180fdf56a7b

Tx prefix hash: c0b1bcc3d7b730fccdb8fa90e571bd15dc6e7d2ac467d0e3d2b01de4fc038631
Tx public key: 22fc9ff715f69856862d1bf6ffc94fba7739a7ef79fb507564f25f27502c1b8e
Timestamp: 1711817598 Timestamp [UCT]: 2024-03-30 16:53:18 Age [y:d:h:m:s]: 01:248:07:56:08
Block: 989735 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 436181 RingCT/type: yes/0
Extra: 0122fc9ff715f69856862d1bf6ffc94fba7739a7ef79fb507564f25f27502c1b8e02110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9e30d14a5320babd8e2cb90154da35dea26ac8fbe35e7c83c5a7838168cc2467 0.600000000000 1450053 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": 989745, "vin": [ { "gen": { "height": 989735 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9e30d14a5320babd8e2cb90154da35dea26ac8fbe35e7c83c5a7838168cc2467" } } ], "extra": [ 1, 34, 252, 159, 247, 21, 246, 152, 86, 134, 45, 27, 246, 255, 201, 79, 186, 119, 57, 167, 239, 121, 251, 80, 117, 100, 242, 95, 39, 80, 44, 27, 142, 2, 17, 0, 0, 0, 3, 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