Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6144eaeab5e7bf12f8d93ea645c5130ec1ce2579f69376fe2a0f526f31468140

Tx prefix hash: 663ace61f94b2a7eb4df35e05638518b043cfba5e6dd02e3d86c49288c3c4a04
Tx public key: c2414772e686c5ab5a4c9067816bb6a9b20070ae71a6205d49320126848e6a4d
Timestamp: 1748497254 Timestamp [UCT]: 2025-05-29 05:40:54 Age [y:d:h:m:s]: 00:175:22:21:40
Block: 1293279 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 123411 RingCT/type: yes/0
Extra: 01c2414772e686c5ab5a4c9067816bb6a9b20070ae71a6205d49320126848e6a4d021100000001df096e52000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 134d573cdd70ea3f54cbe769f3254cb64288bf6e2df580af41ee2ed33ff06915 0.600000000000 1780750 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": 1293289, "vin": [ { "gen": { "height": 1293279 } } ], "vout": [ { "amount": 600000000, "target": { "key": "134d573cdd70ea3f54cbe769f3254cb64288bf6e2df580af41ee2ed33ff06915" } } ], "extra": [ 1, 194, 65, 71, 114, 230, 134, 197, 171, 90, 76, 144, 103, 129, 107, 182, 169, 178, 0, 112, 174, 113, 166, 32, 93, 73, 50, 1, 38, 132, 142, 106, 77, 2, 17, 0, 0, 0, 1, 223, 9, 110, 82, 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