Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5f3d1514560cb94d17190f299dfc864d6548a84f21ae4570eafe05e8a2464ac2

Tx prefix hash: bb48d6df548497cf5641b2bc1ef08a694adf2b79da87f87d2fc4552a862cbe18
Tx public key: 7f8052bb0a0e66b76544440f9df83a81c4a0d3c4daa35e73a3aea606366f933a
Timestamp: 1576643782 Timestamp [UCT]: 2019-12-18 04:36:22 Age [y:d:h:m:s]: 05:135:06:30:47
Block: 28395 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1244319 RingCT/type: yes/0
Extra: 017f8052bb0a0e66b76544440f9df83a81c4a0d3c4daa35e73a3aea606366f933a0211000000059159db1e000000000000000000

1 output(s) for total of 494.215591407000 dcy

stealth address amount amount idx
00: 4ec8e7911d9aef3be3e6fc306436845ea7be87490667130d480fc899eac72d3b 494.215591407000 46939 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": 28405, "vin": [ { "gen": { "height": 28395 } } ], "vout": [ { "amount": 494215591407, "target": { "key": "4ec8e7911d9aef3be3e6fc306436845ea7be87490667130d480fc899eac72d3b" } } ], "extra": [ 1, 127, 128, 82, 187, 10, 14, 102, 183, 101, 68, 68, 15, 157, 248, 58, 129, 196, 160, 211, 196, 218, 163, 94, 115, 163, 174, 166, 6, 54, 111, 147, 58, 2, 17, 0, 0, 0, 5, 145, 89, 219, 30, 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