Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bd8ed362baf6787b9d39c4dc4652e71f6aff6dcb0b0494d047405d7adbc718d2

Tx prefix hash: f73ac559e9c6a206eb8e2c1f28fc11e926270e885e172dcafb0c14eeb818744a
Tx public key: 230dbbb6e63c4d2f0228b410f78a59f2156dceb19378fda994a46c5c181c7323
Timestamp: 1726106872 Timestamp [UCT]: 2024-09-12 02:07:52 Age [y:d:h:m:s]: 00:207:19:11:07
Block: 1108180 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 148336 RingCT/type: yes/0
Extra: 01230dbbb6e63c4d2f0228b410f78a59f2156dceb19378fda994a46c5c181c732302110000000691e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cfd5d8fbe8c8fbc58b9196d443a24d60e5216a1ced2d5adf1cb2346d1ae17573 0.600000000000 1585987 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": 1108190, "vin": [ { "gen": { "height": 1108180 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cfd5d8fbe8c8fbc58b9196d443a24d60e5216a1ced2d5adf1cb2346d1ae17573" } } ], "extra": [ 1, 35, 13, 187, 182, 230, 60, 77, 47, 2, 40, 180, 16, 247, 138, 89, 242, 21, 109, 206, 177, 147, 120, 253, 169, 148, 164, 108, 92, 24, 28, 115, 35, 2, 17, 0, 0, 0, 6, 145, 225, 60, 4, 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