Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 182292a55b81f8d0c4b7ae37ce6a590edbf07e1924cbc0628d2659fbfa0676e1

Tx prefix hash: 55250cdc9585210c8d998011da4b7480e45d81df0a2db0e60d53d0b1cae775c3
Tx public key: 3e2c5f1987cfd4403544d5376c273ab305e993c6edd1d2f68e76d7541d90796a
Timestamp: 1711141214 Timestamp [UCT]: 2024-03-22 21:00:14 Age [y:d:h:m:s]: 00:361:14:31:28
Block: 984134 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 258540 RingCT/type: yes/0
Extra: 013e2c5f1987cfd4403544d5376c273ab305e993c6edd1d2f68e76d7541d90796a02110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 774031aea6ec0788d0e9ecefcd338e74d79643a369826a1ba224b4e351bca925 0.600000000000 1444293 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": 984144, "vin": [ { "gen": { "height": 984134 } } ], "vout": [ { "amount": 600000000, "target": { "key": "774031aea6ec0788d0e9ecefcd338e74d79643a369826a1ba224b4e351bca925" } } ], "extra": [ 1, 62, 44, 95, 25, 135, 207, 212, 64, 53, 68, 213, 55, 108, 39, 58, 179, 5, 233, 147, 198, 237, 209, 210, 246, 142, 118, 215, 84, 29, 144, 121, 106, 2, 17, 0, 0, 0, 1, 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