Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 22a01088a4be392d826eb949ab4256a95a02d77b6fe369cc605d1fd130fa0ef9

Tx prefix hash: 2d2ef7654e6ea7ec14aef1ae2861155b5db5f394945315856198fb58bbc01696
Tx public key: 63510294e9c9b2e2b98c81f11a338fd4feb2cc51181a15564390a2024e64d6af
Timestamp: 1732160436 Timestamp [UCT]: 2024-11-21 03:40:36 Age [y:d:h:m:s]: 00:137:23:39:08
Block: 1158273 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 98423 RingCT/type: yes/0
Extra: 0163510294e9c9b2e2b98c81f11a338fd4feb2cc51181a15564390a2024e64d6af02110000000b007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9de22033b364f51e4a23d61de1dc6b98e2a0b150f30ab29fae09aa9d79ce6972 0.600000000000 1643902 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": 1158283, "vin": [ { "gen": { "height": 1158273 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9de22033b364f51e4a23d61de1dc6b98e2a0b150f30ab29fae09aa9d79ce6972" } } ], "extra": [ 1, 99, 81, 2, 148, 233, 201, 178, 226, 185, 140, 129, 241, 26, 51, 143, 212, 254, 178, 204, 81, 24, 26, 21, 86, 67, 144, 162, 2, 78, 100, 214, 175, 2, 17, 0, 0, 0, 11, 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