Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5ecd10b16db75a34ca6a4c53fe4149b1b4d3e1493897dd35dba9d50ab813e460

Tx prefix hash: c7dfa6d6f52db470d45df58e6a886084bfc4bed4d895a30a6acd276e32e40b10
Tx public key: 308529505e100470392efa57120b4db45d53984198ab477b72fa30d53c5c7056
Timestamp: 1636879829 Timestamp [UCT]: 2021-11-14 08:50:29 Age [y:d:h:m:s]: 03:165:03:29:19
Block: 374101 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 896480 RingCT/type: yes/0
Extra: 01308529505e100470392efa57120b4db45d53984198ab477b72fa30d53c5c70560211000000141154028c000000000000000000

1 output(s) for total of 35.354807633000 dcy

stealth address amount amount idx
00: 1b31857044d3a08be46c9e7a4ba1a033d99ff454f6b36638f8d41ea66a4fb04a 35.354807633000 757323 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": 374111, "vin": [ { "gen": { "height": 374101 } } ], "vout": [ { "amount": 35354807633, "target": { "key": "1b31857044d3a08be46c9e7a4ba1a033d99ff454f6b36638f8d41ea66a4fb04a" } } ], "extra": [ 1, 48, 133, 41, 80, 94, 16, 4, 112, 57, 46, 250, 87, 18, 11, 77, 180, 93, 83, 152, 65, 152, 171, 71, 123, 114, 250, 48, 213, 60, 92, 112, 86, 2, 17, 0, 0, 0, 20, 17, 84, 2, 140, 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