Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3f237e97c15723a26285752e4e2c0badf62d5d802daea99263aa557b3fe37bca

Tx prefix hash: b53066e0d7d1c10732acf1c4db103e2dd155c777c7885a9826cd168c9b321d09
Tx public key: 143968e52969574e0b15a2430ed1183c93d6950512fa45cb7bac0d26618e280d
Timestamp: 1577798998 Timestamp [UCT]: 2019-12-31 13:29:58 Age [y:d:h:m:s]: 05:164:22:57:31
Block: 35787 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1267656 RingCT/type: yes/0
Extra: 01143968e52969574e0b15a2430ed1183c93d6950512fa45cb7bac0d26618e280d02110000000dd81c26c0000000000000000000

1 output(s) for total of 467.114842253000 dcy

stealth address amount amount idx
00: a3c46384cb52be4f4af4d4798c49d5adaad645c2a4cf4c5f39ae794df504881f 467.114842253000 60417 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": 35797, "vin": [ { "gen": { "height": 35787 } } ], "vout": [ { "amount": 467114842253, "target": { "key": "a3c46384cb52be4f4af4d4798c49d5adaad645c2a4cf4c5f39ae794df504881f" } } ], "extra": [ 1, 20, 57, 104, 229, 41, 105, 87, 78, 11, 21, 162, 67, 14, 209, 24, 60, 147, 214, 149, 5, 18, 250, 69, 203, 123, 172, 13, 38, 97, 142, 40, 13, 2, 17, 0, 0, 0, 13, 216, 28, 38, 192, 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