Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1306d15391a63c211eb249474d85c4e9e1490c67e82a7a3863effd14fe6990e6

Tx prefix hash: 7d2c9edbca8067e717c8960e42c8942fca1e8de8b3178827c89e6ec1c08bdf32
Tx public key: 659a0931ebc8d64deaa38cdcee28d50bfd4ed3dcb7ebb9bc14ffb0f309ffe571
Timestamp: 1729112230 Timestamp [UCT]: 2024-10-16 20:57:10 Age [y:d:h:m:s]: 00:038:17:09:36
Block: 1133102 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 27636 RingCT/type: yes/0
Extra: 01659a0931ebc8d64deaa38cdcee28d50bfd4ed3dcb7ebb9bc14ffb0f309ffe5710211000000043cd0fc06000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9be03ecc0a367a19f44a974fe59c379d13f56d1406c906afa5d2ed5b6daf7b86 0.600000000000 1616171 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": 1133112, "vin": [ { "gen": { "height": 1133102 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9be03ecc0a367a19f44a974fe59c379d13f56d1406c906afa5d2ed5b6daf7b86" } } ], "extra": [ 1, 101, 154, 9, 49, 235, 200, 214, 77, 234, 163, 140, 220, 238, 40, 213, 11, 253, 78, 211, 220, 183, 235, 185, 188, 20, 255, 176, 243, 9, 255, 229, 113, 2, 17, 0, 0, 0, 4, 60, 208, 252, 6, 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