Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 30ffac69d1810313b9ac11f593d7b1b94052dc1f20739df310619c7c57c62e72

Tx prefix hash: 765bdf864a43875f2861de22175d61a7a0b6c34d4c3a0b29dd3681c05362e511
Tx public key: 09eb20d852ad39c8c963da38249cf5928a7e3bd35adf64945a37aae4c0d29df9
Timestamp: 1644511119 Timestamp [UCT]: 2022-02-10 16:38:39 Age [y:d:h:m:s]: 03:111:19:14:56
Block: 435756 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 859851 RingCT/type: yes/0
Extra: 0109eb20d852ad39c8c963da38249cf5928a7e3bd35adf64945a37aae4c0d29df902110000000bcb8520c2000000000000000000

1 output(s) for total of 22.088172266000 dcy

stealth address amount amount idx
00: a2d0d936e9739dd03800b81e86cfe1b1bcc5c3bf04793ee1bda86901a43ca64c 22.088172266000 847009 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": 435766, "vin": [ { "gen": { "height": 435756 } } ], "vout": [ { "amount": 22088172266, "target": { "key": "a2d0d936e9739dd03800b81e86cfe1b1bcc5c3bf04793ee1bda86901a43ca64c" } } ], "extra": [ 1, 9, 235, 32, 216, 82, 173, 57, 200, 201, 99, 218, 56, 36, 156, 245, 146, 138, 126, 59, 211, 90, 223, 100, 148, 90, 55, 170, 228, 192, 210, 157, 249, 2, 17, 0, 0, 0, 11, 203, 133, 32, 194, 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