Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 07dbeef4e69897407099ba7b9fc4e2109503cb2da54779a134cad226fae47d6c

Tx prefix hash: 4e20f87b9ee85b9cb34a248d5f0e85d6e8499e867f4cdaacb03aa7381e15c0ce
Tx public key: 3a16f6a4e54511a5102e0233111005b5c03ac755ce7d28309fd3219ea2ad1572
Timestamp: 1702262665 Timestamp [UCT]: 2023-12-11 02:44:25 Age [y:d:h:m:s]: 01:333:05:13:15
Block: 910499 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 497017 RingCT/type: yes/0
Extra: 013a16f6a4e54511a5102e0233111005b5c03ac755ce7d28309fd3219ea2ad1572021100000002e6d27f9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 79ef687fe28a2fe8063dc63764c0783f1674d9da37fce1c2e1183427decd300b 0.600000000000 1367660 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": 910509, "vin": [ { "gen": { "height": 910499 } } ], "vout": [ { "amount": 600000000, "target": { "key": "79ef687fe28a2fe8063dc63764c0783f1674d9da37fce1c2e1183427decd300b" } } ], "extra": [ 1, 58, 22, 246, 164, 229, 69, 17, 165, 16, 46, 2, 51, 17, 16, 5, 181, 192, 58, 199, 85, 206, 125, 40, 48, 159, 211, 33, 158, 162, 173, 21, 114, 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