Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dd338a47acd43c629fb3bbad03ab59c5fc5b6e44b80af877f2cafe010dd2541f

Tx prefix hash: d8970df8c908d6e9d59f5cab885950d73ba0ecd1117d9563ad3fc784e519ab89
Tx public key: 334ed4959afa7fda85dc1ce094b34d98d90d80d5d227c53bd01715f625908a69
Timestamp: 1706504231 Timestamp [UCT]: 2024-01-29 04:57:11 Age [y:d:h:m:s]: 01:123:00:29:47
Block: 945649 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 349049 RingCT/type: yes/0
Extra: 01334ed4959afa7fda85dc1ce094b34d98d90d80d5d227c53bd01715f625908a6902110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 32bc4fdf9f9559287b5b7cbd1977ca7fa753a4002d999a2157482257347a9a9c 0.600000000000 1403965 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": 945659, "vin": [ { "gen": { "height": 945649 } } ], "vout": [ { "amount": 600000000, "target": { "key": "32bc4fdf9f9559287b5b7cbd1977ca7fa753a4002d999a2157482257347a9a9c" } } ], "extra": [ 1, 51, 78, 212, 149, 154, 250, 127, 218, 133, 220, 28, 224, 148, 179, 77, 152, 217, 13, 128, 213, 210, 39, 197, 59, 208, 23, 21, 246, 37, 144, 138, 105, 2, 17, 0, 0, 0, 3, 82, 212, 126, 148, 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