Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f4cf3371d6df9cab78836c735a9094b02efb7f35c5403873a7781ba1971719b7

Tx prefix hash: 89e99c965d8b0bd3a60bbd8a155c392ce1c55ff7ec6215d4d88bfb0b84444f8b
Tx public key: 8650e88477786333e0ce414e276340f5d6c0be4d2c50dfb4cd3f426da3f9cecf
Timestamp: 1741037954 Timestamp [UCT]: 2025-03-03 21:39:14 Age [y:d:h:m:s]: 00:262:15:38:57
Block: 1231509 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 185456 RingCT/type: yes/0
Extra: 018650e88477786333e0ce414e276340f5d6c0be4d2c50dfb4cd3f426da3f9cecf021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1c3bba02fd56c3842d51177e233c6dee3d3ac9dfe5ea5dbe40685d15096ef9de 0.600000000000 1718416 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": 1231519, "vin": [ { "gen": { "height": 1231509 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1c3bba02fd56c3842d51177e233c6dee3d3ac9dfe5ea5dbe40685d15096ef9de" } } ], "extra": [ 1, 134, 80, 232, 132, 119, 120, 99, 51, 224, 206, 65, 78, 39, 99, 64, 245, 214, 192, 190, 77, 44, 80, 223, 180, 205, 63, 66, 109, 163, 249, 206, 207, 2, 17, 0, 0, 0, 5, 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