Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f25ae8a5265a4ae75bf652a0ab363c1fa8f1d39ddbec1d6cde48d04b99dda6d7

Tx prefix hash: 9783dbd2162dd6750807e716ad7cc62ccbb4421ce6c6ffb671af460555120aa4
Tx public key: 909fa817df3d9181b1ceab7e8c9b27ca77e35336defb5c52c257c5557889ac68
Timestamp: 1735646747 Timestamp [UCT]: 2024-12-31 12:05:47 Age [y:d:h:m:s]: 00:351:09:28:04
Block: 1187141 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 248698 RingCT/type: yes/0
Extra: 01909fa817df3d9181b1ceab7e8c9b27ca77e35336defb5c52c257c5557889ac68021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: afc5625077e1bf7e74d286e2bd2c86bf4a3185d6a52a6cf6885ed27a76902706 0.600000000000 1673628 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": 1187151, "vin": [ { "gen": { "height": 1187141 } } ], "vout": [ { "amount": 600000000, "target": { "key": "afc5625077e1bf7e74d286e2bd2c86bf4a3185d6a52a6cf6885ed27a76902706" } } ], "extra": [ 1, 144, 159, 168, 23, 223, 61, 145, 129, 177, 206, 171, 126, 140, 155, 39, 202, 119, 227, 83, 54, 222, 251, 92, 82, 194, 87, 197, 85, 120, 137, 172, 104, 2, 17, 0, 0, 0, 4, 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