Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 594fa9389614796e03dfb4d856b0aa122ae97183408395258b6510cdfff1aa0c

Tx prefix hash: aa357a729bae90faba78aaf44ff5be698bc686abd3926482e9c28b233997b051
Tx public key: 7acdab89ffcba7472ffeaef5da581ff50d833fcb917142ea76e1b98dca0b551e
Timestamp: 1672958698 Timestamp [UCT]: 2023-01-05 22:44:58 Age [y:d:h:m:s]: 02:103:10:27:42
Block: 668421 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 595622 RingCT/type: yes/0
Extra: 017acdab89ffcba7472ffeaef5da581ff50d833fcb917142ea76e1b98dca0b551e021100000006e6d27f9c000000000000000000

1 output(s) for total of 3.743205858000 dcy

stealth address amount amount idx
00: 99153f98e2f77a2bb78257acc7e58a9a5a8285596516eea4f9abb8153b5423e2 3.743205858000 1109668 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": 668431, "vin": [ { "gen": { "height": 668421 } } ], "vout": [ { "amount": 3743205858, "target": { "key": "99153f98e2f77a2bb78257acc7e58a9a5a8285596516eea4f9abb8153b5423e2" } } ], "extra": [ 1, 122, 205, 171, 137, 255, 203, 167, 71, 47, 254, 174, 245, 218, 88, 31, 245, 13, 131, 63, 203, 145, 113, 66, 234, 118, 225, 185, 141, 202, 11, 85, 30, 2, 17, 0, 0, 0, 6, 230, 210, 127, 156, 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