Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9148da7f4c63df325da5d3bf9ece4f085cfdfe9ecc09abc73d47720c0df2674d

Tx prefix hash: e79206c419b971ca8ba3c58387fc7fcea754472d272cd697f6e9c5ef7957355a
Tx public key: cfcd24adf5811049dab79f97648dce9654ae9a8043d44ee5fce3de8cb8a0e699
Timestamp: 1675277078 Timestamp [UCT]: 2023-02-01 18:44:38 Age [y:d:h:m:s]: 01:287:09:58:15
Block: 687662 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 466344 RingCT/type: yes/0
Extra: 01cfcd24adf5811049dab79f97648dce9654ae9a8043d44ee5fce3de8cb8a0e6990211000000015029cbac000000000000000000

1 output(s) for total of 3.232140739000 dcy

stealth address amount amount idx
00: e0721fbb8d4ae3f5862d62d20cc37824ebf9c4659f2f714fed1b6c1f950b24be 3.232140739000 1130243 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": 687672, "vin": [ { "gen": { "height": 687662 } } ], "vout": [ { "amount": 3232140739, "target": { "key": "e0721fbb8d4ae3f5862d62d20cc37824ebf9c4659f2f714fed1b6c1f950b24be" } } ], "extra": [ 1, 207, 205, 36, 173, 245, 129, 16, 73, 218, 183, 159, 151, 100, 141, 206, 150, 84, 174, 154, 128, 67, 212, 78, 229, 252, 227, 222, 140, 184, 160, 230, 153, 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