Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 100249cb31559bcf45fd846fc8f2bb431c1c751ee7f083b8cf297b47f5704153

Tx prefix hash: 328a11bb51c432fcb42b32dca767a56e2eb89c40ee89e6b670622429f92be160
Tx public key: 641a2a8db27b5c19b271b8e674fda8db9a184c138b243f6aabbca8906c35b04f
Timestamp: 1724989310 Timestamp [UCT]: 2024-08-30 03:41:50 Age [y:d:h:m:s]: 00:213:14:49:06
Block: 1098911 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 152532 RingCT/type: yes/0
Extra: 01641a2a8db27b5c19b271b8e674fda8db9a184c138b243f6aabbca8906c35b04f02110000000791e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 758a2bd437300b248f8599330ce69bca99f2191196d063cf5171a0994561de3a 0.600000000000 1574792 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": 1098921, "vin": [ { "gen": { "height": 1098911 } } ], "vout": [ { "amount": 600000000, "target": { "key": "758a2bd437300b248f8599330ce69bca99f2191196d063cf5171a0994561de3a" } } ], "extra": [ 1, 100, 26, 42, 141, 178, 123, 92, 25, 178, 113, 184, 230, 116, 253, 168, 219, 154, 24, 76, 19, 139, 36, 63, 106, 171, 188, 168, 144, 108, 53, 176, 79, 2, 17, 0, 0, 0, 7, 145, 225, 60, 4, 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