Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4900a8f0d3334216c714975ee6b8634d4eab5a4d18b7e43043162241c17a6ed3

Tx prefix hash: 472ba50f60c7b4fb7aa072271a041ff92f55b9180b86cfca6c318d5b329dfa68
Tx public key: 7e666719aa770588f78b0db9fc8a14f0514c6178d804617400ff7c7f168b8364
Timestamp: 1736029951 Timestamp [UCT]: 2025-01-04 22:32:31 Age [y:d:h:m:s]: 00:306:16:33:00
Block: 1190325 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 216684 RingCT/type: yes/0
Extra: 017e666719aa770588f78b0db9fc8a14f0514c6178d804617400ff7c7f168b836402110000000125a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 159dbf1e3e5f63821cc70b567c75d3497be17e189420f2c8d4925709dc3f2c28 0.600000000000 1676840 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": 1190335, "vin": [ { "gen": { "height": 1190325 } } ], "vout": [ { "amount": 600000000, "target": { "key": "159dbf1e3e5f63821cc70b567c75d3497be17e189420f2c8d4925709dc3f2c28" } } ], "extra": [ 1, 126, 102, 103, 25, 170, 119, 5, 136, 247, 139, 13, 185, 252, 138, 20, 240, 81, 76, 97, 120, 216, 4, 97, 116, 0, 255, 124, 127, 22, 139, 131, 100, 2, 17, 0, 0, 0, 1, 37, 163, 90, 15, 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