Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c312d73cc6be1aa5c0e0a9da3d464aa3eda0ff785b26080034cf2ce341d8eafc

Tx prefix hash: 010eb63ce3fd8f7e02af1f0441ca9ab12edeca34ed15b38e195f217f5946f802
Tx public key: 8dfc0fe4eaa4d0cbad9009d496ba5f68ee2403532f11929d833290e948cd71cc
Timestamp: 1607090233 Timestamp [UCT]: 2020-12-04 13:57:13 Age [y:d:h:m:s]: 03:346:22:59:37
Block: 155483 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 998772 RingCT/type: yes/0
Extra: 018dfc0fe4eaa4d0cbad9009d496ba5f68ee2403532f11929d833290e948cd71cc02110000039b123756c7000000000000000000

1 output(s) for total of 187.432040905000 dcy

stealth address amount amount idx
00: a3f5da6569c1bda67822450394eef9749c1b8e3ded2de58f6de7f10bb5297fd9 187.432040905000 263112 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": 155493, "vin": [ { "gen": { "height": 155483 } } ], "vout": [ { "amount": 187432040905, "target": { "key": "a3f5da6569c1bda67822450394eef9749c1b8e3ded2de58f6de7f10bb5297fd9" } } ], "extra": [ 1, 141, 252, 15, 228, 234, 164, 208, 203, 173, 144, 9, 212, 150, 186, 95, 104, 238, 36, 3, 83, 47, 17, 146, 157, 131, 50, 144, 233, 72, 205, 113, 204, 2, 17, 0, 0, 3, 155, 18, 55, 86, 199, 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