Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 660dfba7841fcbfb7abf50fc921588fbc475cf6c4183ff5dc93116310bbe980b

Tx prefix hash: b1a81c71c33613d0d2fe856c87e10b0a4c5630eef0b82e272cdc45ecc4d7e9b0
Tx public key: 79b2f2718dc261365a8a5fd2b55a563426503e3fba33a676182cd62b7668af0e
Timestamp: 1666043424 Timestamp [UCT]: 2022-10-17 21:50:24 Age [y:d:h:m:s]: 02:085:06:08:43
Block: 611250 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 582804 RingCT/type: yes/0
Extra: 0179b2f2718dc261365a8a5fd2b55a563426503e3fba33a676182cd62b7668af0e02110000000a33af99f4000000000000000000

1 output(s) for total of 5.789953174000 dcy

stealth address amount amount idx
00: eee95ae27f2b05c44ed22ce06b7aa8d4440b0afe848c34627686a418889e8f0f 5.789953174000 1048312 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": 611260, "vin": [ { "gen": { "height": 611250 } } ], "vout": [ { "amount": 5789953174, "target": { "key": "eee95ae27f2b05c44ed22ce06b7aa8d4440b0afe848c34627686a418889e8f0f" } } ], "extra": [ 1, 121, 178, 242, 113, 141, 194, 97, 54, 90, 138, 95, 210, 181, 90, 86, 52, 38, 80, 62, 63, 186, 51, 166, 118, 24, 44, 214, 43, 118, 104, 175, 14, 2, 17, 0, 0, 0, 10, 51, 175, 153, 244, 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