Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4b4f683e823d0927243b62b437e62e03a399a393c55909dafbf24b9ee374f2b2

Tx prefix hash: 33256d41ec08e5a5eeaba07154707e6f4facb54b9ce680d388b5c8a066a6a862
Tx public key: c89d93f3d16c84d491f221f0bb473729f4f4aaee2135150d9c3aae56d4d402f8
Timestamp: 1733656842 Timestamp [UCT]: 2024-12-08 11:20:42 Age [y:d:h:m:s]: 00:193:00:41:14
Block: 1170682 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 137650 RingCT/type: yes/0
Extra: 01c89d93f3d16c84d491f221f0bb473729f4f4aaee2135150d9c3aae56d4d402f80211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b77b4ac8b078bdaa1c9582ac557de26d5a7b974f571f8c5148a6a39167f3f940 0.600000000000 1656413 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": 1170692, "vin": [ { "gen": { "height": 1170682 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b77b4ac8b078bdaa1c9582ac557de26d5a7b974f571f8c5148a6a39167f3f940" } } ], "extra": [ 1, 200, 157, 147, 243, 209, 108, 132, 212, 145, 242, 33, 240, 187, 71, 55, 41, 244, 244, 170, 238, 33, 53, 21, 13, 156, 58, 174, 86, 212, 212, 2, 248, 2, 17, 0, 0, 0, 4, 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