Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 050d05d91f7ddbd20b9be2b3ea4a5139acfea6c673186409de3d4e080b8d5f00

Tx prefix hash: a448478ab19a1aa7ee917a229f52786b8c4f2bd37a796601779443d89ad54f97
Tx public key: 57b9c45327f5cd4bb084d299a9346ee4a68a305e0a3f44d726eb83a3d01b8dd8
Timestamp: 1695950998 Timestamp [UCT]: 2023-09-29 01:29:58 Age [y:d:h:m:s]: 01:184:20:30:48
Block: 858384 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 393165 RingCT/type: yes/0
Extra: 0157b9c45327f5cd4bb084d299a9346ee4a68a305e0a3f44d726eb83a3d01b8dd8021100000001e6d27f9c000000000000000000

1 output(s) for total of 0.878653251000 dcy

stealth address amount amount idx
00: ad344ec06c272139dca5bd4f60e8b7c1a985d0e4146a494350695def56bbc13d 0.878653251000 1312556 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": 858394, "vin": [ { "gen": { "height": 858384 } } ], "vout": [ { "amount": 878653251, "target": { "key": "ad344ec06c272139dca5bd4f60e8b7c1a985d0e4146a494350695def56bbc13d" } } ], "extra": [ 1, 87, 185, 196, 83, 39, 245, 205, 75, 176, 132, 210, 153, 169, 52, 110, 228, 166, 138, 48, 94, 10, 63, 68, 215, 38, 235, 131, 163, 208, 27, 141, 216, 2, 17, 0, 0, 0, 1, 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