Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 897a1387ee3b66f9a55afb479b1d7e0c72d52f6a332e8243161d0a4a41a24f31

Tx prefix hash: ab560efe7040dccf54ae67fd3eca8e4007b3d01e71cafe3e57979c1867bf8c71
Tx public key: 01139c9dc21fa12ea0ecb9e4a81d32e2e94189caaa0a336c8e2ee3a2a46ee144
Timestamp: 1701484272 Timestamp [UCT]: 2023-12-02 02:31:12 Age [y:d:h:m:s]: 01:177:16:21:26
Block: 904037 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 388191 RingCT/type: yes/0
Extra: 0101139c9dc21fa12ea0ecb9e4a81d32e2e94189caaa0a336c8e2ee3a2a46ee14402110000000475e3f0e9000000000000000000

1 output(s) for total of 0.620226207000 dcy

stealth address amount amount idx
00: 30db7a960335da5009c2eca4bb6b3bd2649fcf17a3304076245e93622c3779f5 0.620226207000 1360740 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": 904047, "vin": [ { "gen": { "height": 904037 } } ], "vout": [ { "amount": 620226207, "target": { "key": "30db7a960335da5009c2eca4bb6b3bd2649fcf17a3304076245e93622c3779f5" } } ], "extra": [ 1, 1, 19, 156, 157, 194, 31, 161, 46, 160, 236, 185, 228, 168, 29, 50, 226, 233, 65, 137, 202, 170, 10, 51, 108, 142, 46, 227, 162, 164, 110, 225, 68, 2, 17, 0, 0, 0, 4, 117, 227, 240, 233, 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