Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: de74cbbe4942ff7d6b3ca4b30dec409d9f06baf4cde8d21abef1718754bfe5d1

Tx prefix hash: 33243166eec4ccb43ec9b2ebbff773bdfa00498bda0ea950cd4a134061f5a700
Tx public key: 490510c563c1d8f3631d546047f36350680473405683a80acd6280a45ab3e719
Timestamp: 1657028493 Timestamp [UCT]: 2022-07-05 13:41:33 Age [y:d:h:m:s]: 02:347:07:30:30
Block: 537203 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 769293 RingCT/type: yes/0
Extra: 01490510c563c1d8f3631d546047f36350680473405683a80acd6280a45ab3e719021100000002bf7ee4e7000000000000000000

1 output(s) for total of 10.186467607000 dcy

stealth address amount amount idx
00: cc4ae103410f4d0dce21aa4a524d5257edd2ac555c44129ed0f1af6caa8a1a2b 10.186467607000 967066 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": 537213, "vin": [ { "gen": { "height": 537203 } } ], "vout": [ { "amount": 10186467607, "target": { "key": "cc4ae103410f4d0dce21aa4a524d5257edd2ac555c44129ed0f1af6caa8a1a2b" } } ], "extra": [ 1, 73, 5, 16, 197, 99, 193, 216, 243, 99, 29, 84, 96, 71, 243, 99, 80, 104, 4, 115, 64, 86, 131, 168, 10, 205, 98, 128, 164, 90, 179, 231, 25, 2, 17, 0, 0, 0, 2, 191, 126, 228, 231, 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