Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0edf97272cd9a3e0571ea7e1ed16903cd9832619535998554e560dc05baadcd4

Tx prefix hash: 858bd1b15f355571abdf30eb50eb1de0d93384e2c24b10ac703db7828c36ec73
Tx public key: 0c1d840b3eb75d04b6d0a99a712b61e37f5ae9972878ff4cfada6eb2619bcefd
Timestamp: 1682862799 Timestamp [UCT]: 2023-04-30 13:53:19 Age [y:d:h:m:s]: 01:264:22:19:41
Block: 749922 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 450780 RingCT/type: yes/0
Extra: 010c1d840b3eb75d04b6d0a99a712b61e37f5ae9972878ff4cfada6eb2619bcefd02110000000533af99f4000000000000000000

1 output(s) for total of 2.010005796000 dcy

stealth address amount amount idx
00: 3fd8a49311dc10e64320059e5280d5b3cd44cfdc98c2867b3a865e974136d7c1 2.010005796000 1197943 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": 749932, "vin": [ { "gen": { "height": 749922 } } ], "vout": [ { "amount": 2010005796, "target": { "key": "3fd8a49311dc10e64320059e5280d5b3cd44cfdc98c2867b3a865e974136d7c1" } } ], "extra": [ 1, 12, 29, 132, 11, 62, 183, 93, 4, 182, 208, 169, 154, 113, 43, 97, 227, 127, 90, 233, 151, 40, 120, 255, 76, 250, 218, 110, 178, 97, 155, 206, 253, 2, 17, 0, 0, 0, 5, 51, 175, 153, 244, 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