Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a4f87e6d1a11c1db9213cbac1d769757840dea2b91cafe893fbe854c25d047b7

Tx prefix hash: db2225276dddb5a375d227821c93c10cb883dfb773726fbab5efc5047322d57e
Tx public key: a989fcb402de57c9cfa22a5a7d7104a4f63f43197e35d63680d9f78c1338487a
Timestamp: 1710475982 Timestamp [UCT]: 2024-03-15 04:13:02 Age [y:d:h:m:s]: 01:061:05:38:16
Block: 978617 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 304759 RingCT/type: yes/0
Extra: 01a989fcb402de57c9cfa22a5a7d7104a4f63f43197e35d63680d9f78c1338487a0211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a27433947e63dfbf18f5b1a76059a4b1b61e509f8638b20082e99544e984d0a6 0.600000000000 1438644 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": 978627, "vin": [ { "gen": { "height": 978617 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a27433947e63dfbf18f5b1a76059a4b1b61e509f8638b20082e99544e984d0a6" } } ], "extra": [ 1, 169, 137, 252, 180, 2, 222, 87, 201, 207, 162, 42, 90, 125, 113, 4, 164, 246, 63, 67, 25, 126, 53, 214, 54, 128, 217, 247, 140, 19, 56, 72, 122, 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