Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e9487a22a7de15d310e198bb78f7045ff4de36eb6395c42958757bc2194c584d

Tx prefix hash: b44d1c08097ac4e092ae7c0dc767998398cf7a238a079b6b3156ab8a8ce5cb1a
Tx public key: f851ab18b9522d323ae32c5990de416414e40f3cf684ea5894eb8909a0761432
Timestamp: 1702084986 Timestamp [UCT]: 2023-12-09 01:23:06 Age [y:d:h:m:s]: 01:050:18:05:04
Block: 909026 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 297406 RingCT/type: yes/0
Extra: 01f851ab18b9522d323ae32c5990de416414e40f3cf684ea5894eb8909a0761432021100000002faf35c9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 33c6b9a33d0ffcba07fd0737f47b93e70be66d7fb2822803123d8fcc1b906217 0.600000000000 1366091 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": 909036, "vin": [ { "gen": { "height": 909026 } } ], "vout": [ { "amount": 600000000, "target": { "key": "33c6b9a33d0ffcba07fd0737f47b93e70be66d7fb2822803123d8fcc1b906217" } } ], "extra": [ 1, 248, 81, 171, 24, 185, 82, 45, 50, 58, 227, 44, 89, 144, 222, 65, 100, 20, 228, 15, 60, 246, 132, 234, 88, 148, 235, 137, 9, 160, 118, 20, 50, 2, 17, 0, 0, 0, 2, 250, 243, 92, 156, 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