Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ebc62a8f874aa6ee6fe69621c5175bbee9a63ee79259a67d46c52ac790dbb37c

Tx prefix hash: 0061fba7772ada6628138d2bebd4cac16eb3632030b68abfbcaec519e93cb263
Tx public key: 365c3c81f7b4d64f338c17b7601f79e40277e95723519f49a39a8099bf2fd9f0
Timestamp: 1702861620 Timestamp [UCT]: 2023-12-18 01:07:00 Age [y:d:h:m:s]: 01:338:12:34:43
Block: 915470 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 500795 RingCT/type: yes/0
Extra: 01365c3c81f7b4d64f338c17b7601f79e40277e95723519f49a39a8099bf2fd9f0021100000002e6d27f9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1ab026da76edbdd21bad717eba8c7b7983725a9a9ebcd5ab2d483c80118843d4 0.600000000000 1372866 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": 915480, "vin": [ { "gen": { "height": 915470 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1ab026da76edbdd21bad717eba8c7b7983725a9a9ebcd5ab2d483c80118843d4" } } ], "extra": [ 1, 54, 92, 60, 129, 247, 180, 214, 79, 51, 140, 23, 183, 96, 31, 121, 228, 2, 119, 233, 87, 35, 81, 159, 73, 163, 154, 128, 153, 191, 47, 217, 240, 2, 17, 0, 0, 0, 2, 230, 210, 127, 156, 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