Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 16274b9bbe11a6c48143c7893e1e1c5d5f47cac65da2cee7700ffe8899717203

Tx prefix hash: 11adb5e0d2c3ae40119f07c4f354e36abd8cef0df1397c50e4e9e3876661deeb
Tx public key: 3316324e34eaaff841800820e852a1c43632010c8bd6c4b06980e4d45bea05d9
Timestamp: 1733514955 Timestamp [UCT]: 2024-12-06 19:55:55 Age [y:d:h:m:s]: 00:114:16:42:58
Block: 1169497 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 81775 RingCT/type: yes/0
Extra: 013316324e34eaaff841800820e852a1c43632010c8bd6c4b06980e4d45bea05d9021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ba6bad8c63d78e9db44c6f0bdf571796d5314799b00c1b6cd0c30190cfb4043f 0.600000000000 1655216 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": 1169507, "vin": [ { "gen": { "height": 1169497 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ba6bad8c63d78e9db44c6f0bdf571796d5314799b00c1b6cd0c30190cfb4043f" } } ], "extra": [ 1, 51, 22, 50, 78, 52, 234, 175, 248, 65, 128, 8, 32, 232, 82, 161, 196, 54, 50, 1, 12, 139, 214, 196, 176, 105, 128, 228, 212, 91, 234, 5, 217, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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