Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9b7c0867255c862ca85f2909d80875c3d863c4e8fefd1127207b618d8c188f18

Tx prefix hash: 16c14310c3a09858880b989c7fe6c89ffcc3cc0fe4c9e520245ba4e30bc7140b
Tx public key: 3d002a7a4d41a86707935036d61e170cf17fc8a08e4a2eb849222e55e0cc4630
Timestamp: 1682582001 Timestamp [UCT]: 2023-04-27 07:53:21 Age [y:d:h:m:s]: 02:000:08:38:54
Block: 747588 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 522400 RingCT/type: yes/0
Extra: 013d002a7a4d41a86707935036d61e170cf17fc8a08e4a2eb849222e55e0cc4630021100000001e6d27f9c000000000000000000

1 output(s) for total of 2.046178698000 dcy

stealth address amount amount idx
00: 46d93723c3b1f48d20fb025e7b06d000ec571c1d8359afc9abd31a6c2eb49a06 2.046178698000 1195293 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": 747598, "vin": [ { "gen": { "height": 747588 } } ], "vout": [ { "amount": 2046178698, "target": { "key": "46d93723c3b1f48d20fb025e7b06d000ec571c1d8359afc9abd31a6c2eb49a06" } } ], "extra": [ 1, 61, 0, 42, 122, 77, 65, 168, 103, 7, 147, 80, 54, 214, 30, 23, 12, 241, 127, 200, 160, 142, 74, 46, 184, 73, 34, 46, 85, 224, 204, 70, 48, 2, 17, 0, 0, 0, 1, 230, 210, 127, 156, 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