Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 149479b1a5213e523e0658df0aab19a26815a7d611648d2db43e71965e342f27

Tx prefix hash: 899ee342bd8cac8c195238722e57c300dadf19262494d9764592df16c65a0bc0
Tx public key: c94ed1bb455f817b6673e41f936a17e82a1f4cf079d3248291d7ae1a4c49925e
Timestamp: 1720181953 Timestamp [UCT]: 2024-07-05 12:19:13 Age [y:d:h:m:s]: 01:149:18:56:35
Block: 1059060 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 365614 RingCT/type: yes/0
Extra: 01c94ed1bb455f817b6673e41f936a17e82a1f4cf079d3248291d7ae1a4c49925e02110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cdd13985efbb28485c4d5888c1ba729aae581da1fcac3d63cd22e3d346115225 0.600000000000 1529521 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": 1059070, "vin": [ { "gen": { "height": 1059060 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cdd13985efbb28485c4d5888c1ba729aae581da1fcac3d63cd22e3d346115225" } } ], "extra": [ 1, 201, 78, 209, 187, 69, 95, 129, 123, 102, 115, 228, 31, 147, 106, 23, 232, 42, 31, 76, 240, 121, 211, 36, 130, 145, 215, 174, 26, 76, 73, 146, 94, 2, 17, 0, 0, 0, 4, 89, 218, 211, 245, 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