Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4afebecbc606ffc724678d627b96ddf150ee780d67564aa5152bd5c76170e644

Tx prefix hash: 9434d700f5ec97f97238835ac56ae0dc3f92b234b227c5506704f0799cb3cb1a
Tx public key: 219aac28cf6c515203bd0c0d473c97dbec910fcd34eff5bf4faf59b7afa5e16e
Timestamp: 1699569084 Timestamp [UCT]: 2023-11-09 22:31:24 Age [y:d:h:m:s]: 01:222:02:18:24
Block: 888177 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 419831 RingCT/type: yes/0
Extra: 01219aac28cf6c515203bd0c0d473c97dbec910fcd34eff5bf4faf59b7afa5e16e021100000002e6d27f9c000000000000000000

1 output(s) for total of 0.700004610000 dcy

stealth address amount amount idx
00: f8305ae16c4161791a5206d697ca336e3d83523bc44c7af39a56b7a8fdcdec4c 0.700004610000 1344108 of 0

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": 888187, "vin": [ { "gen": { "height": 888177 } } ], "vout": [ { "amount": 700004610, "target": { "key": "f8305ae16c4161791a5206d697ca336e3d83523bc44c7af39a56b7a8fdcdec4c" } } ], "extra": [ 1, 33, 154, 172, 40, 207, 108, 81, 82, 3, 189, 12, 13, 71, 60, 151, 219, 236, 145, 15, 205, 52, 239, 245, 191, 79, 175, 89, 183, 175, 165, 225, 110, 2, 17, 0, 0, 0, 2, 230, 210, 127, 156, 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