Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c7c98aad4380aa64abecd9ab7a3592746bc2bf0dd2f8f36be149e727c1cbe9bd

Tx prefix hash: b7707a334156c7ef1be9b73783c64538ea0644f679fa7239de784c170a7d4d2a
Tx public key: c3cc6b1c01c794c09cfb991a0d52c70883b93dd1855ebd9cac73cd099666c7e1
Timestamp: 1703198003 Timestamp [UCT]: 2023-12-21 22:33:23 Age [y:d:h:m:s]: 01:021:07:30:55
Block: 918253 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 276586 RingCT/type: yes/0
Extra: 01c3cc6b1c01c794c09cfb991a0d52c70883b93dd1855ebd9cac73cd099666c7e102110000000c0011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0e2aa4057d1669bf23febead7064b6f9d364194dc751e0ab2f33a67470fbca70 0.600000000000 1375895 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": 918263, "vin": [ { "gen": { "height": 918253 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0e2aa4057d1669bf23febead7064b6f9d364194dc751e0ab2f33a67470fbca70" } } ], "extra": [ 1, 195, 204, 107, 28, 1, 199, 148, 192, 156, 251, 153, 26, 13, 82, 199, 8, 131, 185, 61, 209, 133, 94, 189, 156, 172, 115, 205, 9, 150, 102, 199, 225, 2, 17, 0, 0, 0, 12, 0, 17, 5, 91, 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