Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 378fbef53175c101ff054c68b718899dc0db90d44a11af0a53b325d09f6e7eff

Tx prefix hash: 00519be68eba7a3fe5c297cbfe004b74e0ad261f2db82029a914d9cb7a72056c
Tx public key: 2d7d4ad074619007e927b1f29cdf6743a9666b9e98f4996968d2fa0155f4e1a5
Timestamp: 1678652233 Timestamp [UCT]: 2023-03-12 20:17:13 Age [y:d:h:m:s]: 02:037:13:08:45
Block: 715659 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 548392 RingCT/type: yes/0
Extra: 012d7d4ad074619007e927b1f29cdf6743a9666b9e98f4996968d2fa0155f4e1a50211000000025029cbac000000000000000000

1 output(s) for total of 2.610505059000 dcy

stealth address amount amount idx
00: 21d21459e1ea6d93d7a3be3b17d2efd04870f8b72e53fca2e6e9bf68d9438f31 2.610505059000 1159962 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": 715669, "vin": [ { "gen": { "height": 715659 } } ], "vout": [ { "amount": 2610505059, "target": { "key": "21d21459e1ea6d93d7a3be3b17d2efd04870f8b72e53fca2e6e9bf68d9438f31" } } ], "extra": [ 1, 45, 125, 74, 208, 116, 97, 144, 7, 233, 39, 177, 242, 156, 223, 103, 67, 169, 102, 107, 158, 152, 244, 153, 105, 104, 210, 250, 1, 85, 244, 225, 165, 2, 17, 0, 0, 0, 2, 80, 41, 203, 172, 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