Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1fd4022cfe4f010e0b13f8ccac4215ea3e195e8b02349ed0835f6c58bf0a0987

Tx prefix hash: 2d60dc553a384d2bc269483d3754f05b87d7795cbdc310d87d076a5cdf2a6721
Tx public key: 8b59e9330137207c01d5aef517ffce1ccf39b7c2e8470dc91acae443a2950c28
Timestamp: 1737352816 Timestamp [UCT]: 2025-01-20 06:00:16 Age [y:d:h:m:s]: 00:149:12:36:27
Block: 1201225 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 106602 RingCT/type: yes/0
Extra: 018b59e9330137207c01d5aef517ffce1ccf39b7c2e8470dc91acae443a2950c2802110000000a1f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2f056b67d1428866ea347118784f6df8f4d602d43abdebe81acab80a37e35194 0.600000000000 1687874 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": 1201235, "vin": [ { "gen": { "height": 1201225 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2f056b67d1428866ea347118784f6df8f4d602d43abdebe81acab80a37e35194" } } ], "extra": [ 1, 139, 89, 233, 51, 1, 55, 32, 124, 1, 213, 174, 245, 23, 255, 206, 28, 207, 57, 183, 194, 232, 71, 13, 201, 26, 202, 228, 67, 162, 149, 12, 40, 2, 17, 0, 0, 0, 10, 31, 10, 83, 235, 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