Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f22d00ce9eac14ac646ea3b02dccf2363285bd1f8026738769e486cb3ce4f7e0

Tx prefix hash: 8921d7e0b0f753969f405508db5239855b3156770f094fdda12adf7b6872e531
Tx public key: e50b4d13916f1a5db39d1a52d957176253edbdeb8d5bebcf3ca1f72fd3ae573d
Timestamp: 1729924158 Timestamp [UCT]: 2024-10-26 06:29:18 Age [y:d:h:m:s]: 00:238:19:09:39
Block: 1139796 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 170331 RingCT/type: yes/0
Extra: 01e50b4d13916f1a5db39d1a52d957176253edbdeb8d5bebcf3ca1f72fd3ae573d0211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ffd37e77913e1cfdd51563279bc9509dbbffa700594924c5b99c23d0de6cdaf6 0.600000000000 1623583 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": 1139806, "vin": [ { "gen": { "height": 1139796 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ffd37e77913e1cfdd51563279bc9509dbbffa700594924c5b99c23d0de6cdaf6" } } ], "extra": [ 1, 229, 11, 77, 19, 145, 111, 26, 93, 179, 157, 26, 82, 217, 87, 23, 98, 83, 237, 189, 235, 141, 91, 235, 207, 60, 161, 247, 47, 211, 174, 87, 61, 2, 17, 0, 0, 0, 1, 31, 10, 83, 235, 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