Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 45ba75cb322f8e02e831ac2813c89ce76ab9e55b8eaa8a50fe7617157ae0e2c4

Tx prefix hash: 80a977edc6020f331e14f7439a77c1241fe44e998b09dbb762c950e9e193dee1
Tx public key: 95c35de25446284fc1eeb5e85a9fad01b0a207c7cfbd2118c742f93d0764c402
Timestamp: 1704525363 Timestamp [UCT]: 2024-01-06 07:16:03 Age [y:d:h:m:s]: 01:086:09:25:11
Block: 929237 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 322854 RingCT/type: yes/0
Extra: 0195c35de25446284fc1eeb5e85a9fad01b0a207c7cfbd2118c742f93d0764c4020211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7a7c015518b6a668feacf1afe6553972c9f46c4238c454aca1ee98626dfb0b7c 0.600000000000 1387107 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": 929247, "vin": [ { "gen": { "height": 929237 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7a7c015518b6a668feacf1afe6553972c9f46c4238c454aca1ee98626dfb0b7c" } } ], "extra": [ 1, 149, 195, 93, 226, 84, 70, 40, 79, 193, 238, 181, 232, 90, 159, 173, 1, 176, 162, 7, 199, 207, 189, 33, 24, 199, 66, 249, 61, 7, 100, 196, 2, 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