Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 790975a6c45e64443ab174fceed9e431f6642a3d5ee10bc2805adafd47921dd6

Tx prefix hash: 1b0407ae3082ba61b12db4c8021ccd09971306b104beb57e3eb69ffd6985aef2
Tx public key: 6b0de643a9f5025582c2d85a1d604648401b2777afdea4c821f8e91b04ae41d1
Timestamp: 1749287034 Timestamp [UCT]: 2025-06-07 09:03:54 Age [y:d:h:m:s]: 00:159:04:39:23
Block: 1299805 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 111458 RingCT/type: yes/0
Extra: 016b0de643a9f5025582c2d85a1d604648401b2777afdea4c821f8e91b04ae41d1021100000003bf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 05a12da9e089547cdd6265fa38f10d36efefb600251ab7f843b3037d30c7ca78 0.600000000000 1787344 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": 1299815, "vin": [ { "gen": { "height": 1299805 } } ], "vout": [ { "amount": 600000000, "target": { "key": "05a12da9e089547cdd6265fa38f10d36efefb600251ab7f843b3037d30c7ca78" } } ], "extra": [ 1, 107, 13, 230, 67, 169, 245, 2, 85, 130, 194, 216, 90, 29, 96, 70, 72, 64, 27, 39, 119, 175, 222, 164, 200, 33, 248, 233, 27, 4, 174, 65, 209, 2, 17, 0, 0, 0, 3, 191, 81, 178, 162, 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