Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a361647cb900b23f0d51695fc7910a507a39f02851304a97cb21a2fcb49b5de6

Tx prefix hash: a3bec91417dc32d393ad11dcf731f7d73dcf1838a963d97ee7a6f384dcbfc1ab
Tx public key: e6df7ff9a9d978e972b29f67ad97e1a1acdeeb9cb11ccba1df2a5b08cdc19929
Timestamp: 1704301221 Timestamp [UCT]: 2024-01-03 17:00:21 Age [y:d:h:m:s]: 01:103:20:19:10
Block: 927410 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 335326 RingCT/type: yes/0
Extra: 01e6df7ff9a9d978e972b29f67ad97e1a1acdeeb9cb11ccba1df2a5b08cdc199290211000000040011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7c27723edb8e0971e55aaf24ad92fa5c9dc33d1e5f314da3a799ba672568eae3 0.600000000000 1385246 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": 927420, "vin": [ { "gen": { "height": 927410 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7c27723edb8e0971e55aaf24ad92fa5c9dc33d1e5f314da3a799ba672568eae3" } } ], "extra": [ 1, 230, 223, 127, 249, 169, 217, 120, 233, 114, 178, 159, 103, 173, 151, 225, 161, 172, 222, 235, 156, 177, 28, 203, 161, 223, 42, 91, 8, 205, 193, 153, 41, 2, 17, 0, 0, 0, 4, 0, 17, 5, 91, 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