Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8d102341e531300d64416937621ddd36ce1d7b85f73d109fd1a63be02f35178b

Tx prefix hash: 3427b7a2e327cc9adff2951950796456a3e7fae1aacb38159442f5f144a9d961
Tx public key: ae014b041bd7080ecdf844c7afa05ab84654aeba61b3cc12c18bb18f03e71ee4
Timestamp: 1674980839 Timestamp [UCT]: 2023-01-29 08:27:19 Age [y:d:h:m:s]: 01:250:01:58:11
Block: 685196 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 439703 RingCT/type: yes/0
Extra: 01ae014b041bd7080ecdf844c7afa05ab84654aeba61b3cc12c18bb18f03e71ee402110000000675e3f0e9000000000000000000

1 output(s) for total of 3.293526397000 dcy

stealth address amount amount idx
00: 2e1e1fb74a31d0a08723480234c35b465ee57a3e03abcbd9010c03d5b06edf56 3.293526397000 1127485 of 0

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": 685206, "vin": [ { "gen": { "height": 685196 } } ], "vout": [ { "amount": 3293526397, "target": { "key": "2e1e1fb74a31d0a08723480234c35b465ee57a3e03abcbd9010c03d5b06edf56" } } ], "extra": [ 1, 174, 1, 75, 4, 27, 215, 8, 14, 205, 248, 68, 199, 175, 160, 90, 184, 70, 84, 174, 186, 97, 179, 204, 18, 193, 139, 177, 143, 3, 231, 30, 228, 2, 17, 0, 0, 0, 6, 117, 227, 240, 233, 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