Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f559f31935913a68764ac9a8dcbe8c99ddfde71613897badd4424a33627d2803

Tx prefix hash: 5fb0e87465fc798cd820ade9799ac58cf06145b9b7eb42516a5e8dabcc546faa
Tx public key: ca3c595a00b7881793765f3d3cbc28cce1fc1c884e325e3a2d7ae3aa6c232d40
Timestamp: 1705283680 Timestamp [UCT]: 2024-01-15 01:54:40 Age [y:d:h:m:s]: 00:362:02:40:53
Block: 935521 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 259269 RingCT/type: yes/0
Extra: 01ca3c595a00b7881793765f3d3cbc28cce1fc1c884e325e3a2d7ae3aa6c232d4002110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4c212160d5020e38f09b4cef71d5fd0227d975a9b1ff449dc6c0e58536312abc 0.600000000000 1393537 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": 935531, "vin": [ { "gen": { "height": 935521 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4c212160d5020e38f09b4cef71d5fd0227d975a9b1ff449dc6c0e58536312abc" } } ], "extra": [ 1, 202, 60, 89, 90, 0, 183, 136, 23, 147, 118, 95, 61, 60, 188, 40, 204, 225, 252, 28, 136, 78, 50, 94, 58, 45, 122, 227, 170, 108, 35, 45, 64, 2, 17, 0, 0, 0, 1, 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