Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3c7cabc645d5ad137e01928dc1658fa729f79521a8d7c727d3b8fd2848ae0db4

Tx prefix hash: 75c8be839481fb4fbdc902db2e3f2bd91424644aed4ba245dead0b4fdf341d7d
Tx public key: f8d22e07a7e4e5fa0bc7110e7d5a75fc465261bec144d50984daf81a70e2d523
Timestamp: 1675178017 Timestamp [UCT]: 2023-01-31 15:13:37 Age [y:d:h:m:s]: 02:077:16:41:11
Block: 686834 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 577171 RingCT/type: yes/0
Extra: 01f8d22e07a7e4e5fa0bc7110e7d5a75fc465261bec144d50984daf81a70e2d5230211000000015029cbac000000000000000000

1 output(s) for total of 3.252623326000 dcy

stealth address amount amount idx
00: 4425d0d42ac6b1a3be30c3d24e49e54ebd7b1e5155049abfe12d57b4e205928d 3.252623326000 1129372 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": 686844, "vin": [ { "gen": { "height": 686834 } } ], "vout": [ { "amount": 3252623326, "target": { "key": "4425d0d42ac6b1a3be30c3d24e49e54ebd7b1e5155049abfe12d57b4e205928d" } } ], "extra": [ 1, 248, 210, 46, 7, 167, 228, 229, 250, 11, 199, 17, 14, 125, 90, 117, 252, 70, 82, 97, 190, 193, 68, 213, 9, 132, 218, 248, 26, 112, 226, 213, 35, 2, 17, 0, 0, 0, 1, 80, 41, 203, 172, 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