Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e5e979ff031e594f8f62c1e14813d4040b0ee3f5438d0e8b40ff96c7cbed4700

Tx prefix hash: 047d384fda840cfe63b27cf7160a09cd7b7e4f2582370fd0d76f1c69035c52ca
Tx public key: 129a20ae1e6e355de8065278659e66d43a0463737233201d9c80a7c85da9e51b
Timestamp: 1735272672 Timestamp [UCT]: 2024-12-27 04:11:12 Age [y:d:h:m:s]: 00:084:02:01:02
Block: 1184047 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 59889 RingCT/type: yes/0
Extra: 01129a20ae1e6e355de8065278659e66d43a0463737233201d9c80a7c85da9e51b0211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 020f08eb2237f2c86abc81a6f0fa9ccfdee938e2f36c0bb7c008eb0ac6aecc08 0.600000000000 1670500 of 15

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": 1184057, "vin": [ { "gen": { "height": 1184047 } } ], "vout": [ { "amount": 600000000, "target": { "key": "020f08eb2237f2c86abc81a6f0fa9ccfdee938e2f36c0bb7c008eb0ac6aecc08" } } ], "extra": [ 1, 18, 154, 32, 174, 30, 110, 53, 93, 232, 6, 82, 120, 101, 158, 102, 212, 58, 4, 99, 115, 114, 51, 32, 29, 156, 128, 167, 200, 93, 169, 229, 27, 2, 17, 0, 0, 0, 1, 31, 10, 83, 235, 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