Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c68ccb50d8d753e2d9290faf83aa8a1ca73ba40624d89d8b8adff5a5fcb4a8f0

Tx prefix hash: 83ab40981dedd83afc659ff7d9f1ba4b5b4b688743b53ea9340f37935f924ad9
Tx public key: a186a3e59b785a2d1a5030268e1a78d69d44e92afc99b53ab7078b5a26398dd5
Timestamp: 1740370386 Timestamp [UCT]: 2025-02-24 04:13:06 Age [y:d:h:m:s]: 00:269:17:39:06
Block: 1225963 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 190552 RingCT/type: yes/0
Extra: 01a186a3e59b785a2d1a5030268e1a78d69d44e92afc99b53ab7078b5a26398dd50211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5026f2e881c13b6e240b24b73d2e92fbdf627178c2a078a3958cf6ad3ff6444f 0.600000000000 1712834 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": 1225973, "vin": [ { "gen": { "height": 1225963 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5026f2e881c13b6e240b24b73d2e92fbdf627178c2a078a3958cf6ad3ff6444f" } } ], "extra": [ 1, 161, 134, 163, 229, 155, 120, 90, 45, 26, 80, 48, 38, 142, 26, 120, 214, 157, 68, 233, 42, 252, 153, 181, 58, 183, 7, 139, 90, 38, 57, 141, 213, 2, 17, 0, 0, 0, 1, 31, 10, 83, 235, 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