Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3dd60bcc63734adf519f226fd897ab546d2cbd330f65b094b328dc68c9d395a8

Tx prefix hash: 58066bee5f60b4e8ff43f3998d39cefc26412531b95c65b845f551abc5318791
Tx public key: 542dcd69a1f9b861c7ec32d4e86499516fd0bdc419a666d093dd44f7406140d6
Timestamp: 1717979305 Timestamp [UCT]: 2024-06-10 00:28:25 Age [y:d:h:m:s]: 00:143:04:49:06
Block: 1040806 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 102493 RingCT/type: yes/0
Extra: 01542dcd69a1f9b861c7ec32d4e86499516fd0bdc419a666d093dd44f7406140d602110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 31916d81c055c8e7d8bedab8de86e2cd062d54d1fa7038305a8a4b5d02cf6555 0.600000000000 1509469 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": 1040816, "vin": [ { "gen": { "height": 1040806 } } ], "vout": [ { "amount": 600000000, "target": { "key": "31916d81c055c8e7d8bedab8de86e2cd062d54d1fa7038305a8a4b5d02cf6555" } } ], "extra": [ 1, 84, 45, 205, 105, 161, 249, 184, 97, 199, 236, 50, 212, 232, 100, 153, 81, 111, 208, 189, 196, 25, 166, 102, 208, 147, 221, 68, 247, 64, 97, 64, 214, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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