Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9fe04f735c24d4ae2923e15648a01d33096d22f7ecc52b7c84f17e41c5e542cb

Tx prefix hash: 016082f9c9915b0ca60d21e4596f197c8e46e04caa3bce99260192cb76bc0712
Tx public key: 95a3a55a7439f9658edc42a018a239542d437e24aa27cfdd54f8bf100b51409c
Timestamp: 1727036006 Timestamp [UCT]: 2024-09-22 20:13:26 Age [y:d:h:m:s]: 00:205:06:07:55
Block: 1115893 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 146520 RingCT/type: yes/0
Extra: 0195a3a55a7439f9658edc42a018a239542d437e24aa27cfdd54f8bf100b51409c02110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7beb76cfad7f1caf252e7e497c73078d1fd4b2a1bc867a13e9854843db05602d 0.600000000000 1596182 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": 1115903, "vin": [ { "gen": { "height": 1115893 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7beb76cfad7f1caf252e7e497c73078d1fd4b2a1bc867a13e9854843db05602d" } } ], "extra": [ 1, 149, 163, 165, 90, 116, 57, 249, 101, 142, 220, 66, 160, 24, 162, 57, 84, 45, 67, 126, 36, 170, 39, 207, 221, 84, 248, 191, 16, 11, 81, 64, 156, 2, 17, 0, 0, 0, 4, 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