Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a9be6e7df82a863eed00a4ee8cc3182e1d75902fae5f391d345ad7a06d406ad7

Tx prefix hash: 7f31970dc570de2fd653d1b683a674389eecfd7e7c72768c5aeae97d8ba43871
Tx public key: a8ce2380606b09b9056556d8147915e5ac30d54542b2653e6de5f5c87b49a978
Timestamp: 1714245921 Timestamp [UCT]: 2024-04-27 19:25:21 Age [y:d:h:m:s]: 00:303:02:01:10
Block: 1009847 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 216637 RingCT/type: yes/0
Extra: 01a8ce2380606b09b9056556d8147915e5ac30d54542b2653e6de5f5c87b49a9780211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2673904c8e880b05792953c2118f725ca9bb73aac3e51e525b7df11402e299ae 0.600000000000 1471635 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": 1009857, "vin": [ { "gen": { "height": 1009847 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2673904c8e880b05792953c2118f725ca9bb73aac3e51e525b7df11402e299ae" } } ], "extra": [ 1, 168, 206, 35, 128, 96, 107, 9, 185, 5, 101, 86, 216, 20, 121, 21, 229, 172, 48, 213, 69, 66, 178, 101, 62, 109, 229, 245, 200, 123, 73, 169, 120, 2, 17, 0, 0, 0, 4, 122, 156, 244, 199, 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