Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: add355bc30ba9624585d161a00c60308c4b549d853afa40a0bb5ae66c2941161

Tx prefix hash: f1692348304821a2ec03b17f45c4a3ebdffe07d7ddd0dc24d51b5a612abb6a56
Tx public key: f75077bba7823ff2342af825a4a85f4b203975f7ff4c6d06eea5346e50f2b2e9
Timestamp: 1739012637 Timestamp [UCT]: 2025-02-08 11:03:57 Age [y:d:h:m:s]: 00:283:22:34:20
Block: 1214748 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 200684 RingCT/type: yes/0
Extra: 01f75077bba7823ff2342af825a4a85f4b203975f7ff4c6d06eea5346e50f2b2e9021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f1061a9b0e3b41154373ea539f7b8ecdcbbddb1fc0fb46e6af9eda0d462e8095 0.600000000000 1701543 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": 1214758, "vin": [ { "gen": { "height": 1214748 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f1061a9b0e3b41154373ea539f7b8ecdcbbddb1fc0fb46e6af9eda0d462e8095" } } ], "extra": [ 1, 247, 80, 119, 187, 167, 130, 63, 242, 52, 42, 248, 37, 164, 168, 95, 75, 32, 57, 117, 247, 255, 76, 109, 6, 238, 165, 52, 110, 80, 242, 178, 233, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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