Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2a7c139407b03464404c792177c7980bcb0b36dbff717cf75810cbf2764995e0

Tx prefix hash: e58585cb342aca0bb223b5a2a65d52387122e3a974606cb98ce2f747689afbf1
Tx public key: aa4f64788394fa2deb4ef8a1290f88a97db6c6ebcf10a72bc28f7a6e063b81d4
Timestamp: 1706222079 Timestamp [UCT]: 2024-01-25 22:34:39 Age [y:d:h:m:s]: 01:133:20:57:09
Block: 943303 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 356820 RingCT/type: yes/0
Extra: 01aa4f64788394fa2deb4ef8a1290f88a97db6c6ebcf10a72bc28f7a6e063b81d402110000000552d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f0ff327a3367b2ebac206f5adb860ee63b9dee1a5c93005c5e70a5ff72de3f09 0.600000000000 1401509 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": 943313, "vin": [ { "gen": { "height": 943303 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f0ff327a3367b2ebac206f5adb860ee63b9dee1a5c93005c5e70a5ff72de3f09" } } ], "extra": [ 1, 170, 79, 100, 120, 131, 148, 250, 45, 235, 78, 248, 161, 41, 15, 136, 169, 125, 182, 198, 235, 207, 16, 167, 43, 194, 143, 122, 110, 6, 59, 129, 212, 2, 17, 0, 0, 0, 5, 82, 212, 126, 148, 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