Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9eccf631d3ef12781b2822195f95a8ff6f5e1847cb608de44756a7995ab2fee4

Tx prefix hash: 04b53fbf73867e2e419528a665c1ad33f6562811fd73aa7d48f4c5d95fcf3e90
Tx public key: 9a2e9b6c17fba12d2286013802160f89868c411594c250c7dc08e27b8348ef10
Timestamp: 1577644110 Timestamp [UCT]: 2019-12-29 18:28:30 Age [y:d:h:m:s]: 04:364:20:14:59
Block: 34479 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1149882 RingCT/type: yes/0
Extra: 019a2e9b6c17fba12d2286013802160f89868c411594c250c7dc08e27b8348ef100211000000048a2ee0d9000000000000000000

1 output(s) for total of 471.799651560000 dcy

stealth address amount amount idx
00: ba47e8b757c4731d3cbf28fce0e1eeb28641590c5ba20bc940386faa3fe794e1 471.799651560000 58029 of 0

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": 34489, "vin": [ { "gen": { "height": 34479 } } ], "vout": [ { "amount": 471799651560, "target": { "key": "ba47e8b757c4731d3cbf28fce0e1eeb28641590c5ba20bc940386faa3fe794e1" } } ], "extra": [ 1, 154, 46, 155, 108, 23, 251, 161, 45, 34, 134, 1, 56, 2, 22, 15, 137, 134, 140, 65, 21, 148, 194, 80, 199, 220, 8, 226, 123, 131, 72, 239, 16, 2, 17, 0, 0, 0, 4, 138, 46, 224, 217, 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