Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e323fbf22e7f03a5d867bba4cd6b5d3564987e67aa6c94c1c608b3bab681bac2

Tx prefix hash: dc23496878c2aa29b91f6fe8319019a19bce1155315ecc23f4a258ad526fd088
Tx public key: 369ee8b31b90e10c43910f5a614e622a96d57f9d74642f2d45c4fcc258f15ca9
Timestamp: 1711269403 Timestamp [UCT]: 2024-03-24 08:36:43 Age [y:d:h:m:s]: 00:225:22:14:12
Block: 985197 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 161717 RingCT/type: yes/0
Extra: 01369ee8b31b90e10c43910f5a614e622a96d57f9d74642f2d45c4fcc258f15ca902110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4be939e3648c47c43b1486a02767bc5fa201c4b80daabae3de2e29031fc77aed 0.600000000000 1445406 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": 985207, "vin": [ { "gen": { "height": 985197 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4be939e3648c47c43b1486a02767bc5fa201c4b80daabae3de2e29031fc77aed" } } ], "extra": [ 1, 54, 158, 232, 179, 27, 144, 225, 12, 67, 145, 15, 90, 97, 78, 98, 42, 150, 213, 127, 157, 116, 100, 47, 45, 69, 196, 252, 194, 88, 241, 92, 169, 2, 17, 0, 0, 0, 3, 89, 218, 211, 245, 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